Did you actually experience this issue?

Changes in DB schema mandate Migration?

The DB schema itself does not change here. quota_total is already nullable in the exported Room schema, because the embedded quota object is nullable. This change only aligns the Kotlin model nullability with the existing schema/API behavior, so no migration is required.

I also checked the backend path: the drives endpoint can legitimately return an empty value list, and quota can be serialized as {} when quota information is unavailable, e.g. when the backend quota call is unimplemented/unavailable. The added tests cover both cases.

Did you actually experience this issue?

Not from a production crash report on my side; I found it while checking edge cases around the drives response. The current code is still reproducibly unsafe for valid backend responses: an empty value list hits first(), and quota: {} hits quota.total!!.